Description

Motivation and Context

Closes #[ticket]

Ok so a few things:

• the API only allows for 1 of term / cycle at a time, so the checkbox will have to wait for the API to be updated to accept a list of possible terms / cycles
• I didn't make it location bc a dependent ticket is that we have some pre-defined list of acceptable cities / locations. I.e. the location field in the form needs to be a combobox
• you can't hit enter inside of the select / dropdown so I took the liberty to add a search button
• The search bar no longer makes sense for the companies page
  • I think we can abstract it so that search-bar is changed to search-bar-roles and then we add a search-bar-companies because having workTerm or cycle doesn't really apply to companies.
  • This also requires us to think about the home page search bar. Right now it's literally just the search bar but I think we can have an option above to search between Roles / Companies and that will be used as a prop for the search-filter component. The search filter then displays the corresponding search-bar based on that prop
  • I want to make a no results found page / component bc it's hard to tell if something is loading or if there are no results so i'm prob gonna do that next

How has this been tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• I have moved the ticket to "In Review"
• I have added reviewers to this PR
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.